Thanks a lot, @jschoone.

I think I'd still like to discuss how we differentiate a Cluster Stack openstack-scs2-v1-33-v1 from version series openstack-scs2-v1-33-* from a series openstack-scs2-*. Naming them all the same will confuse ourselves.
See SovereignCloudStack/sovereigncloudstack.org#65 (comment).

Despite this, I have merged all your improvements, including the ones that removed the "series". I split the commits into groups though, so we can easily revert depending on the outcome of the discussion.

Thanks a lot, @jschoone.

I think I'd still like to discuss how we differentiate a Cluster Stack openstack-scs2-v1-33-v1 from version series openstack-scs2-v1-33-* from a series openstack-scs2-*. Naming them all the same will confuse ourselves. See SovereignCloudStack/sovereigncloudstack.org#65 (comment).

Despite this, I have merged all your improvements, including the ones that removed the "series". I split the commits into groups though, so we can easily revert depending on the outcome of the discussion.

Sorry somehow I completely missed the discussion on that. If calling it "series" makes somehow sense to you and to others you can keep it.
For me personally it's more confusing because this introduces new wording which creates the impression of new concepts. So this probably needs to end up in the glossary as well.

A cluster stack (e.g. scs2) should have a fixed set of addons and features which you can expecte to work on the providers for what the cluster stack is implement. Maybe it can be compared to another software, like Chromium. You can run Chromium on different operating systems, where probably no one says linux-chromium or windows-chromium, but everywhere you expect the same features and behavior. Also it has an engine with an own version (= kubernetes version) and a version for itself (= cluster stack version). Then there are other browsers with the same engine but called Brave or Vivaldi because of some other features. People will say they use the browser Brave, Vivaldi or Chromium and not the "browser series". With those information you can read up which features the browser will get you and you can use them of the operating system (= provider) of your choice.
Not sure if that comparison works, to me it sounds logical :D

If we call scs2 a Cluster Stack, then we should should have different names for scs2-1-33 (maybe "Cluster Stack minor releases"?) and scs2-1-33-v1 (maybe "Cluster Stack release"?).

No strong opinion here ... I intuitively had called scs2-1-33-v1 a Cluster Stack and then we'd need qualifiers for the others. From looking at the way our syself friends use it, is there a clear preference?

@berendt I was approched today again regarding the OSISM-10 that is supposedly part of R9 (and also about the R9 not being visible as well).

Any updates? @berendt ?

What is going to happen with the release notes for R9? I noticed this pending PR today while updating things elsewhere. @SovereignCloudStack/project-board @berendt